Expere Engine and Tools Archived Change Log Entries

Expere Engine 2016.3 Release

The 2016.3 release contains several enhancements, including a new <SignerEmail/> element; a new </eSignatureWKES> acroform field used with fillable text fields; logging enhancements; and the ability to configure DPI for PDF417 Ancillary Barcodes. For detailed information, see the Current Release Change Log Entries section below and Expere Engine and Tools Change Log Entries.

.NET Installation Enhancement

For .NET Expere Implementations, users must download and install vcredist_x64.exe available from Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update before installing the Expere Engine and related components. After installing this file, users must restart IIS.

For more information, refer to Before Installing - .NET Users: Java 8 Requirement in the Expere Implementation Guide.

*** Expere Engine 2016.3 Release - Uniform Closing Dataset (UCD) functionality now supported in Expere Document ServicesDocument Generation Services ***

What is UCD? Uniform Closing Dataset (UCD) is a part of an overall industry movement focused on Data Quality, Transparency and Standardization and is part of the Uniform Mortgage Data Program (UMDP).

What is the purpose? The GSEs are collecting the UCD in order to accomplish the following:

• Provide additional transparency into the mortgage loan file transaction to help assess whether the loan, as closed, meets each GSE's eligibility requirements.
• Provide important information to help enhance the GSEs' ability to detect fraud and misrepresentation at loan delivery.
• Enhance credit risk management with more data and better quality data to help reduce post-purchase data corrections.

What are the benefits? The GSE's developed the UCD to improve the accuracy of how the Closing Disclosure information is communicated and help promote accuracy, consistency, and clarity around the loan transaction.

The Fannie Mae site provides detailed information regarding UCD here.

Important update regarding the Expere Config Tool

It was reported that there is an issue with running Expere Config Tool utility. We are currently working on the fix and will make it available soon. In the meantime, the following Expere Config Tool utility configuration files can be updated manually using a text editor:

• bsi.properties: located at: "C:\inetpub\wwwroot\Expere\bin\bsi.properties"
• web.config.xml: located at "C:\inetpub\wwwroot\Expere\Web.Config"
• log4j.xml: located at "C:\inetpub\wwwroot\Expere\bin\log4j.xml"

To update the Database Settings, navigate to the bsi.properties file; update the following database settings:

• (Hostname) com.bankerssystems.expere.db.Host=""
• (Port) com.bankerssystems.expere.db.Port=""
• (Database) com.bankerssystems.expere.db.Sid=""
• (Username) com.bankerssystems.expere.db.User=""
• (Password) com.bankerssystems.expere.db.Pass=""

To update logging, navigate to log4j.xml file; update the following:

• (Filepath) <param name="File" value="Expere/ExpereIEServicesRequests.log"/>
• (Level) Uncomment out the following:

   <logger name="com.bankerssystems">
   <level value="info" />
   </logger>

  Available options for level value include:

  • info
  • error
  • fatal
  • debug

  Attention: Only one value can be set.

To update the Performance Options, navigate to web.config file, update the following:

• (Min JVM Heap Size - MB) <java.option value="-Xms256m" />
• (Max JVM Heap Size - MB) <java.option value="-Xmx512m" />:

To update the following Certificate Settings, navigate to the bsi.properties.xml file; update the following settings:

• (Key Store Type) keystore.type=""
• (Key Store Provider) keystore.provider=""
• (Key Store URL) keystore.url=""
• (Key Store Password URL) keystore.password.url=""
• (Private Key Password URL) keystore.privatekey.password.url=""
• (Certificate Alias) tamperseal.certificate.alias=""

Previous Release Notes

• Expere Release Notes 2015.2
• Expere Release Notes 2015.2.0.09
• Expere Release Notes 2015.2.0.3260
• Expere Release Notes 2015.2.1
• Expere Release Notes 2015.2.2
• Expere Release Notes 2015.2.3
• Expere Release Notes 2015.3
• Expere Release Notes 2015.3.0.10
• Expere Release Notes 2015.3.0.12

Expere Engine: Ability to produce merged disclosures for either PDF or PDF/A documents

• Type: Enhancement
• Reference: PBI 416499 / 420185 / 421946
• Compliance Impacts: This enhancement is a compliance or regulatory issue.
• Documentation: RequestUCD flag - PDF/A - Expere Developer Guide

Previously in PBI 416188, we enhanced Expere to support the following documents in PDF/A format:

• ClosingDisclosure
• ClosingDisclosureAddendum
• ClosingDisclosure-SellerOnly
• ClosingDisclosure-SellerOnly-Addendum

The request file contains a new <RequestUCD/> element that, when set to "True," produces the documents below in a PDF/A format, and if the addendum is produced, merges it with its respective closing disclosure. The merged document is returned in the response as the closing disclosure instance and the addendum instance is removed. If not setting the flag, documents are produced using the standard PDF format and the documents are not merged.

For more information, see RequestUCD flag - PDF/A in the Expere Developer Guide

As a part of our work for PBI 421946, we also added a new <MergeTRIDDocs/> flag, that when set to "true" in the Expere request, allows users to merge the above closing disclosure documents with an addendum in the normal PDF format. As a result, the closing disclosure, merged with the addendum, is returned in the response with the normal closing disclosure instance name and the addendum instance removed from the response.

PDF/a now available in Expere

• Type: New Feature
• Reference: PBI 416188
• Compliance Impacts: This new feature is not a compliance or regulatory issue.
• Documentation: Expere Developer Guide - PDF/A

Expere users can now produce the following documents in PDF/A format:

• ClosingDisclosure
• ClosingDisclosureAddendum
• ClosingDisclosure-SellerOnly
• ClosingDisclosure-SellerOnly-Addendum

The request file now contains a new <RequestUCD/> element that, when set to "True," produces the documents above. If not setting the flag, documents are produced using the standard PDF format.

What is PDF/A format? It is an ISO 19005 compliance PDF file used for archiving and long-term preservation of electronic documents. For more information, see the following:

• ISO 19005-1:2005
• ISO 19005:2:2011
• ISO 19005:3:2012

SaveInDatabase issue resolved in .XSD files

• Type: Defect correction
• Reference: PBI 373840
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously, users reported that the </SaveInDatabase> was returned in the response file despite not being present in any of the following .XSD files:

• GenerateRequest.xsd
• GenerateResponse.xsd
• SelectAndGenerateRequest.xsd
• SelectAndGenerateResponse.xsd

As a result, when not defining the </SaveInDatabase> value in the request, by default it was set to "True." Transactions were then saved to the database. Users should be able to set the </SaveInDatabase> element to "False."

This behavior has been modified; by default the </SaveInDatabase> element value is now set to "False."

Sequence fields functionality incorporated with MergePDF

• Type: Enhancement
• Reference: PBI 411599 / 410789 41160441080
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: SignaturePoint, FillableCheckbox, FillableText

We have introduced a new <Sequencing/> element to the following field types in the Expere response file:

• Signature (SignaturePoint element)
• Date
• Initials
• FillableText
• FillableCheckboxes

This <Sequencing/> element is implemented for the Secure Document Exchange (SDX) product for those users who sign across documents. It also makes each field unique so ExpereExpere Document ServicesDocument Generation Services can merge PDF documents that use signature, date, initial, and fillable text fields.

If the "MergePDF=true" in the Expere response file, the Signature, Date, Initials, FillableCheckboxes and FillableText field types elements will contain sequencing in the <FieldName/> element using an incremental numbering system with an underscore.

Sequencing logic and format example:

<r:SignaturePointSet> <r:Signer> <r:Id>Homer</r:Id> <- Signer ID <r:Description>Borrower, Borrower</r:Description> <r:SignaturePoints> <r:Type>Initials</r:Type> <r:Sequencing>1</r:Sequencing> <r:FieldName>INI_Borrower_null_homer_false_1_SigField_1</r:FieldName> </r:SignaturePoint> <r:SignaturePoint> <r:IncludeDate>true</r:IncludeDate> <r:PageNumber>1</r:PageNumber> <r:SignatureText>Homer Simpson</r:SignatureText> <r:Type>Signature</r:Type> <r:Sequencing>2</r:Sequencing> <r:FieldName>SIG_Borrower_null_homer_false_1_SigField_2</r:FieldName> </r:SignaturePoint> <r:FillableFieldSet> <r:FillableText> <r:FieldName>FillableField_3</r:FieldName> <r:ToolTip>fill in here</r:ToolTip> <r:PageNumber>1</r:PageNumber> <r:Width>420.0</r:Width> <r:Height>72.0</r:Height> <r:XCoordinate>56.0</r:XCoordinate> <r:YCoordinate>100.0</r:YCoordinate> <r:Sequencing>3</r:Sequencing> </r:FillableText> <FillableCheckBox> <r:FieldName>FillableCheckBox_4</r:FieldName> <r:ToolTip>check here</r:ToolTip> <r:PageNumber>1</r:PageNumber> <r:Checked>false</r:Checked> <r:XCoordinate>22.0</r:XCoordinate> <r:YCoordinate>140.0</r:YCoordinate> <r:Sequencing>4</r:Sequencing> </FillableCheckBox> </r:FillableFieldSet> 

eSignatureWKFS functionality enhancement

• Type: Enhancement
• Reference: PBI 410993
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Reference: Using eSignature and Acroform fields

In a previous release, we added a new element called eSignatureWKES, which allowed Wolters Kluwer Electronic Signature (WKES) users to initial documents with a fillable text field (Acroform). Please refer to change log notes for PBI 408221 - Secure Document Exchange users initials can now render with Acroform fields for past work

We have enhanced this functionality to now follow WKES (previously Secure Document Exchange) naming conventions for initial(s) and checkbox fields. The following behavior now applies:

• If the eSignatureWKES flag is set to "False," the following occurs:
  • Initials are rendered as esignable;
  • Current naming convention is used: <r:FieldName>INI_Borrower_null_homer_false_1_SigField_1</r:FieldName>;
• If the eSignatureWKES flag is set to "True," the following occurs:
  • WKES (previously SDX) naming conventions apply;
  • The <FieldName/> element applies eSignatures for "Initials," "Signature," "Date," and "Checkbox;"

Ability to suppress fillable fields

• Type: Enhancement
• Reference: PBI 413765
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation:

Users may now select which fillable fields, including eSignature fields, appear or do not appear on documents based on a selected package. This functionality is accomplished by supporting an exclusion list per account in the content library which suppresses the fillable fields in any documents included in the list based on the package.

This exclusion list now resides in the .XML file in order to enable this functionality; the .XML file is stored in your custom content folder of the appropriate repository.

.XML structure:

PKG.ABC PKGD.DOC1 PKGD.DOC2 PKG.DEF PKGD.DOC1 PKG.GHI PKGD.DOC1 PKGD.DOC3 

When requesting a transaction for PKG.ABC and that request generates PKGD.DOC1 or PKGD.DOC2, the fillable fields will be suppressed on those two docs, but will remain on all others with fillable fields. If the XML file is empty or the users requests a transaction for a package not in the list, all documents rendered that have fillable fields will be produced with fillable fields.

DiscretePartyID enhanced for static documents

• Type: Enhancement
• Reference: PBI 414317
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously, DiscretePartyID's were only returned for dynamic documents. We have now enhanced the DiscretePartyID functionality to be returned with static documents.

Configuration settings enhanced for OPPSA

• Type: Enhancement
• Reference: PBI 410707
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: Applying OPPSA compatibility configuration changes

Previously, users had to modify transaction data sent to Document Generation Service with the Expere database values.

Users can now apply OPPSA compatibility configuration changes to their appropriate Expere distributed or hosted installation package through database updates. This allow their Expere instance to connect to the Expere OPPSA database to receive policy and organization data and FileSystem content.

For Expere Engine installations, must enter the Expere database information in the bsi.properties file. See Applying OPPSA compatibility configuration changes - .NET Installations for more information.

For JBoss/Wildfly installations, add the database information to the standalone.xml file located in wildfly-10.0.0.Final\standalone\configuration\. See Applying OPPSA compatibility configuration changes - JBoss/Wildfly installations for more information.

SignerEmail element and email address associated with FieldName element added to Expere response file

• Type: Enhancement
• Reference: PBI 410166
• Compliance Impacts: This new feature/enhancement is not a compliance or regulatory issue.
• Documentation: Signer, SignaturePoint

We have implemented the following enhancements to the <SignaturePointSet/> element:

• We have added a new <SignerEmail/> element to the <Signer/> element;
• We have enhanced the <FieldName/> element in the <SignaturePoint/> element to include the email address

These elements appearThis element appears in the Expere response file when including the "eSignatureWKES" flag in the initial request. Sample code below:

<r:SignaturePointSet> <r:Signer> <r:Id>homer</r:Id> <r:SignerEmail>Joe.Doe@wolterskluwer.com</r:SignerEmail> <r:Description>Borrower, Borrower</r:Description> <r:SignaturePoints> <r:SignaturePoint> <r:IncludeDate>true</r:IncludeDate> <r:PageNumber>1</r:PageNumber> <r:PageOrder>1</r:PageOrder> <r:Height>72.0</r:Height> <r:Width>540.0</r:Width> <r:SignatureText>Homer Simpson</r:SignatureText> <r:XCoordinate>36.0</r:XCoordinate> <r:YCoordinate>396.0</r:YCoordinate> <r:Type>Initials</r:Type> <r:FieldName>INI_Borrower_null_homer_false_1_SigField_joe.doe@wolterskluwer.com</r:FieldName> </r:SignaturePoint> </r:SignaturePoints> </r:Signer> </r:SignaturePointSet>

Error logging enhanced

• Reference: PBI 406462
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

As data requirements functionality is not supported in the Hosted Expere application, SCHEMA files are not required. However, missing schema files would cause unnecessary errors in the log files.

We have modified missing schema file requirements; when a document request is made for a document that does not have a corresponding schema file a message is now logged as a warning (WARN) instead of error (ERROR).

SelectGenerate logging enhanced

• Reference: PBI 406459
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously, a SelectAndGenerate document request that did not select any documents resulted in the following errors:

• No packageDocs were specified for processing
• No documents were supplied for assembly

These two responses should not be considered errors. These responses are simply indicating the transaction provided does not meet any of the document autoselection criteria, and therefore did not select any documents.

The log file has been enhanced to now display these two responses under a status of INFO status instead of an ERROR status when a SelectAndGenerate call is inititated but no documents are generated.

signerNames HashMap enhanced

• Reference: PBI 376369
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously, the signerNames HashMap variable was designated as "static;" as a result, the a potential for the following issues existed:

• In com.bankerssystems.expere.render.Signer.java signerNames could be overwitten by separate transactions when Expere processed multiple transactions.
• In com.bankerssystems.expere.render.AncillaryOutputServices.java a transaction could clear out the name of a different transaction.

This issue has been resolved by changing the way SignerName is stored in the Signer class; as a result, the signer name is assigned correctly on a per-transaction basis.

Secure Document Exchange users initials can now render with Acroform fields

• Type: Enhancement
• Reference: PBI 408221
• Compliance Impacts: This new feature is not a compliance or regulatory issue.
• Documentation: Expere Developer's Guide: Using eSignature and Acroform fields

Wolters Kluwer Electronic Signature (WKES) users can now initial documents with a fillable text field (Acroform) using a new element called </eSignatureWKES>, as a child of the </ESignatureAndFieldSupport> element in the </AncillaryOutputOption>. If setting this element to "true," the initials render as a fillable text field on the document(s). By default, this element is set to "false" and renders as an eSignature field. In a future release, WKES users will be able to capture initials one time per signer and populate those initials to all the respective signer fields.

<r:AncillaryOutputOption> <r:OutputType>ESignatureAndFieldSupport</r:OutputType> <r:ESignatureAndFieldSupport> <r:eSignatureTooltip/> <r:eSignatureInitialsTooltip/> <r:eSignatureCoordinatesOnly>false</r:eSignatureCoordinatesOnly> <r:eSignatureDateSupport>true</r:eSignatureDateSupport> <r:NonSignatureFieldCoordinatesOnly>true</r:NonSignatureFieldCoordinatesOnly> <r:eSignatureWKES>false</r:eSignatureWKES> </r:ESignatureAndFieldSupport> </r:AncillaryOutputOption> 

Expere Engine: Ability to configure DPI for PDF417 Ancillary Barcode

• Type: Enhancement
• Reference: PBI 397414
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No documentation update.

Users can now configure the DPI of PDF417 barcodes. This allows users more flexibility when scanning and imaging documents.

In the bsi.properties file, users can set the DPI for the X and Y values, as bolded below.

## Indicates whether 2D barcodes should use DPI or scaling ## If these DPI values are commented out, then scaling will be used. ## 2D Barcode Height and Width are in inches ## com.bankerssystems.expere.model.DpiX=200 ## com.bankerssystems.expere.model.DpiY=200 ## com.bankerssystems.expere.model.2DBarcodeWidth=2.42 ## com.bankerssystems.expere.model.2DBarcodeHeight=0.41 

White space reduced above divider line using Ancillary Barcodes

• Type: Enhancement
• Reference: PBI 393734
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Users reported seeing excessive white space above the divider line in documents containing ancillary barcodes. Code changes were implemented to reduce the white space in the properties.xsl file.

Now when generating a dynamic document with an ancillary barcodes, no unnecessary white space exists above the divider line.

Expere database enhancement

• Type: Defect correction
• Reference: PBI 408584
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: No document impact.

We had previously introduced a new JavaScript caching object that works with Expere file system servers; however, we did not create a similar database caching object for database-only servers. This resulted in users encountering errors accessing the database through the lack of proper authentication credentials.

A JavaScript object that works with Expere databases is currently in development. This enhancement adds authentication credentials to access the database.

Invalid PDF syntax issue addressed through cover sheet generation

• Type: Defect correction
• Reference: PBI 409994
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously when printing a document PDF package with a cover sheet, users reported an Adobe generation error. It was determined that this issue was caused by an invalid PDF syntax in the cover sheet generation method.

This issue has been resolved; a document PDF package with a cover sheet now prints without errors.

Barcode options to honor rows, columns, and error correction level

• Type: Enhancement
• Reference: PBI 405389
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

It was reported that requests containing <Error Correction/>, <Rows/>, and <Columns/> element values, other than the default, were not honored.

We have implemented code changes to honor requests containing non-default values for <Error Correction/>, <Rows/>, and <Columns/> element values.

<exp:AncillaryOutput> <exp:AncillaryOutputOption> <exp:OutputType>Barcode</exp:OutputType> <exp:Barcode> <Type>barcode2D</Type> <UseCoverPage>True</UseCoverPage> <Pattern>577+BMHPF000000000024456+%BRCD%</Pattern> <Barcode2DConfigurationOptions> <ErrorCorrectionLevel>8</ErrorCorrectionLevel> <Columns>5</Columns> <Rows>10</Rows> </Barcode2DConfigurationOptions> </exp:Barcode> </exp:AncillaryOutputOption> </exp:AncillaryOutput> 

New JBoss installation procedure available

• Type: New Feature
• Reference: PBI 405900
• Compliance Impact: This new feature is not a compliance or regulator issue.
• Documentation: Expere JBoss installation

We have created a new standalone JBoss installer for Expere Java users.

Script font enhancements

• Type: Enhancement
• Reference: PBI 405248
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Expere can now print a desired party name in the signature field with a script font type, Pinyon Script. The new script font is embedded into the .PDF document. Additionally, we have added the font to the fonts.xsl file to indicate that we now support Pinyon Script.

PDFMerge updated to use the latest version of iText

• Type: Enhancement
• Reference: PBI 406306
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

As a part of Discrete Party enhancements, we have updated to iText 7 to work with Merged PDF functionality. This enhancement will also allow support of merged PDF with fillable fields and eSignatures in a future release.

See DiscretePartyID for more information on using the <DiscretePartyID/> element.

DiscretePartyID elements added to GetGenerateResponse

• Reference: PBI 405439/405760405770405761
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Documentation: DocInstance, DiscretePartyIDs

The <DiscretePartyID/> element is now available in the Expere Document ServicesExpere Document Generation Services WSDLResponse file in the DocInstance complex type. It is a sibling to the <InstanceDisplayName/> element and a child element of <DocInstance/>.

<DiscretePartyIDs> - 
 <DiscretePartyID>x</DiscretePartyID>
 <DiscretePartyID>x</DiscretePartyID>
</DiscretePartyIDs> 

Generate API enhanced for BRCD values

• Type: Defect Correction
• Reference: PBI 393786
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: No document impact.

It was discovered that .PKG rules were not identified in the Generate API; this resulted in packages having incorrect barcode values. For example: If I have PKG.ABC that has rules to print a value for the BRCD (25 for example), and PKG.XYZ has rules to print a BRCD value of 136, the Generate call applies the first BRCD value vs the PKG identified in the request.

The Generate API ignored the .PKG entered and only applied the data to the documents identified in the request.

The Generate now applies the PKG information to the call when BRCD values apply and subsequently ignore the AutoSelection rules as the documents are pre-identified.

UCD information available in request and response files

• Type: New Feature
• Reference: PBI 397994397990397993
• Compliance Impacts: This new feature is a compliance and regulatory issue.
• Documentation: Uniform Closing Dataset

To comply with the new Uniform Closing Dataset (UCD) requirement, we have implemented new elements in the request and response files for the following API's:

• SelectAndGenerate
• Generate
• SelectGenerateAndDeliver

The request file now contains a new <RequestUCD/> element that, when set to "True," includes UCD information. The response file contains a new <MismoDataSet/> element that wraps the converted MISMO 3.3 converted UCD data.

The Change Log and Important Notifications/ Uniform Closing Dataset (UCD) functionality now supported in the Expere Engine online help topic now contains detailed information on the UCD endeavor.

For more information on using these new elements, see Uniform Closing Dataset.

Expere Engine: ability to clear javascript cache

• Type: Enhancement
• Reference: PBI 401420
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

The Expere IE Cache Manager now allows users to reset the Javascript cache, which stores Javascript files the cache to improve performance.

DocViewer release notes available in Expere Engine and Tools Change Log webhelp

Users can now access the DocViewer release notes ONLINE here.

Form tagline enhancement

• Type: Defect correction
• Reference: PBI 382497
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously, the tagline on custom forms was set to "N," indicating that the form was not a custom form. The expected behavior is that the tagline displays a "Y" to indicate it is a custom form. A typical tagline consists of the following:

• 2014111814.3.2.3023-R20081203N; the "N" indicates that the form is base content; the "N' appeared in all instances.

This issue has been resolved; custom forms are now accurately identified with a "Y" in the tagline.

Expere Engine: continued enhancement of eSignatureAndFieldSupport and SignaturePointSet elements

• Type: New Feature
• Reference: PBI 393921
• Compliance Impacts: This new feature is not a compliance or regulatory issue.
• Documentation: eSignature feature overview, Using eSignature and Acroform fields

Recently, we had implemented SignaturePointSet and eSignatureAndFieldSupport element changes in PBI's 382028 / 392582. With this continued focus we have implemented the following flags for the eSignatureAndFieldSupport element to return X/Y coordinates:

• eSignatureCoordinatesOnly - if set to "true," eSignature fields are suppressed on the form and X/Y coordinates are returned.
• NonSignatureFieldCoordinatesOnly - if set to "true," other Non-Signatures fillable fields (textboxes and checkboxes) are suppressed on the form and X/Y coordinates are returned.

For more information, see the eSignature feature overview section on the Using eSignature and Acroform fields page.

Logging enhancement: FATAL level added

• Type: Enhancement
• Reference: PBI 382127
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Expere Engine: document generation enhanced

• Type: Defect correction
• Reference: PBI 395280
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously, users reported slow performance and time out issues when generating documents. These issues occurred with custom organizations where images existed at a parent level.

When a missing image existed: the system scanned the entire organization tree instead of the requested hierarchy level and incrementally scanning the levels above the original level.

This issue has been resolved; we have addressed the issue above through code changes that have replaced the previous method.

Expere Engine enhanced to utilize JBoss platform

• Type: Enhancement
• Reference: PBI 386541
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: Expere Implementation Guide, Expere System Requirements Guide

We now allow Expere to utilize the JBoss platform. This upgrade requires users to install JBoss and place a new ExpereIEServices_JBoss.ear file in their JBoss installation location. For more information, refer to the Expere Implementation Guide and Expere System Requirements Guide.

Expere Engine: SignaturePointSet and eSignatureAndFieldSupport element changes

• Type: New feature
• Reference: PBI 382028 / 392582
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact. Using eSignature and Acroform fields

In an effort to support returning XY coordinates for all fillable fields we have begun the development work. The first step in supporting this feature is creating a new element (eSignatureAndFieldSupport). See the Using SignaturePointSet and eSignatureAndFieldSupport section in Using eSignature and Acroform fields of the Expere Developer's Guide for details on these two elements.

Java 8 and Saxon upgrade: DB and File System script process available

• Type: Enhancement
• Reference: PBI 376921
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Docmentation: Installation instructions; Powershell and SQL scripts available on your media release

Recently, Java 8, Saxon, and stylesheet upgrades have been implemented; with these upgrades, users must run a script to remove duplicate imports for the database and file system. The scripts are available on your release media at:

See Important update regarding Java 8 and Saxon upgrade: DB and File System script process for detailed information.

.NET Runtime Required Installation Error resolved

• Type: Defect Correction
• Reference: PBI 380115
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: Expere System Requirements Guide

It was reported that when installing Expere Engine 2015.3.0.1355 on Windows Server 2012 R2, a .NET Runtime Required error appeared stating that .NET 4.0 was required. However, Windows Server 2012 includes .NET 4.5.1.

Users were instructed to either click OK on the error message or create the following folder: C:\Windows\Microsoft.NET\Framework\v4.0.30319, then remove the folder after completing the installation.

This issue has been addressed; we have removed the verification that checks the .NET version. Users can now complete the Expere Engine installation without seeing this error message or performing the workaround above.

Expere Engine: Barcode cover sheet enhancement

• Type: Defect Correction and Enhancement
• Reference: PBI 378815
• Compliance Impacts: This defect correction/enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

When utilizing UseCoverPage with the Ancillary Barcode functionality, data within the Instance Display Name elements would overflow off the cover sheet when too long.

This behavior has been enhanced. The Instance Display Name now wraps on the cover sheet. The following text was added to the cover sheet so recipients of the documents know to return the cover sheet with the document:

• “Please include the cover sheet with the associated document for proper processing, when document return is requested.”

Expere Engine: Endpoint URL issue resolved

• Type: Defect Correction
• Reference: PBI 392807
• Compliance Impacts: This defect correction is not a compliance or regulatory issue.
• Documentation: No document impact.

When viewing the endpoint URL (Common/WSEndpoint) with NO transaction data, it was expected that Expere would return the results of the GetServiceInfo call; however, the SAXParser threw an exception due to the absence of data. This resulted in the GetServiceInfo call not occurring.

With the Expere 2016.1.3 hotfix, Expere now successfully returns the results of the GetService Info call when the endpoint is viewed with no transaction data.

Expere Engine: Cash to Close calculated values provided

• Type: Enhancement
• Reference: PBI 385920 / 387587
• Compliance Impacts: This enhancement is a compliance or regulatory issue.
• Documentation: No document impact.
• User Impact: Users who rely on Wolters Kluwer Financial Services for computing totals under “Calculating Cash To Close” on the Loan Estimate are impacted. (“Txn/IntegratedDisclosuresUseExpereComputationsInd” schema point set to “True”.) Those values must be parsed and stored by the user; the stored values must be provided in the Expere transaction when calling for the Closing Disclosure to be used on Page 3 for the “Calculating Cash To Close” section.

The ExpereResponse.xml file now contains Cash to Close calculated values available in a new <r:DocCustomDataItems/> parent element and <r:DocCustomDataItem/> child elements. Each of these elements has a DataItemName attribute and number for the value.

The new Expere Engine stylesheet, AddDocCustomDataItem.xsl, adds these elements as DocCustomDataItems.

The new elements exist as children and grandchildren of the <r:DocDescriptor/> element. The <r:DocCustomDataItem/> elements contain the following DataItemName attribute values:

• /Txn/IntegratedDisclosuresLoanEstimateCashToCloseStoredValueAmount
• /Txn/IntegratedDisclosuresLoanEstimateClosingCostsFinancedStoredValueAmount
• /Txn/IntegratedDisclosuresLoanEstimateTotalClosingCostsStoredValueAmount

The following code snippet appears in the ExpereResponse.xml file:

<r:DocDescriptor> <r:DocID>PKGD.LoanEstimate</r:DocID> <r:DocType>Dynamic</r:DocType> <r:DocDisplayName>Loan Estimate</r:DocDisplayName> <r:DocRootEntityName>INS.LoanEstimate</r:DocRootEntityName> <r:DocCustomDataItems> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateTotalClosingCostsStoredValueAmount">34287</r:DocCustomDataItem> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateClosingCostsFinancedStoredValueAmount">-34287</r:DocCustomDataItem> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateCashToCloseStoredValueAmount">107815</r:DocCustomDataItem> </r:DocCustomDataItems> </r:DocDescriptor>

Expere Engine: Special Character handling enhanced

• Type: Enhancement
• Reference: PBI 374746
• Compliance Impact: This enhancement is not a compliance or regulatory issue
• Documentation: No document impact.

Previously, hosted and non-hosted transactions that called the Expere Engine failed when using certain special characters on static documents.

We have enhanced the Expere Engine to support the following special characters:

Newly Supported:

• 8211: en dash
• 8212: em dash
• 8304: Degree sign
• 9472: Horizontal box

Existing (Previously Supported):

• 8216: left single quotation mark
• 8217: right single quotation mark
• 8220: left double quotation mark
• 8221: right double quotation mark

Foundation for future platform enhancement

• Type: Enhancement
• Reference: PBI 382928
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

We have laid the ground work for a future enhancement to support additional hosted platforms. However, no customer-facing changes currently exist for this change. We will provide additional information as it impacts our users in a future release.

Expere Engine: Enhanced logging for caching and file system repository

• Type: Enhancement
• Reference: PBI 381741
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Logging has been enhanced for the caching and file system repository to help track the progress of requests; these enhancements include the RequestID, OrgID, and PackageID. This enhancement is also a result of the changes made in PBI 382041 below.

Expere Engine: Improved File System indexing

• Type: Enhancement
• Reference: PBI 382041
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Changes were made to the file system repository to make the indexing process more efficient.

Expere Engine: eSignature and AcroForm fields enhanced

• Type: Enhancement
• Reference: PBI 379704, 379926381106
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Documentation: Using eSignature and Acroform fieldsSelect Generate And Deliver, Select And Generate, Generate

Previously, users could not enable or disable eSignatures or AcroForm fields for transactions.

Users can now configure the bsi.properties field to enable or disable eSignature and AcroForm fields in the AncillaryOutput of a SelectAndGenerate or Generate request. Users can now pass eSignature and Acroform values in the AncillaryOutput of a SelectAndGenerate or Generate request. Users can now pass eSignature and Acroform values in the AncillaryOutput of a SelectAndGenerate, Generate, and SelectGenerateAndDeliver request. For detailed information on enabling or disabling eSignature or Acroforms, see Using eSignature and Acroform fields.Select Generate and Deliver, Select And Generate, and Generate.

Expere Config Tool enhanced

• Type: Enhancement
• Reference: PBI 379682
• Compliance Impact: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously, an issue existed in the Expere Config Tool utility in the 2016.1 release (Important update regarding the Expere Config Tool). Users reported an error when launching the Expere Config Tool utility and as a result, could not update various fields.

The Expere Config Tool has been enhanced, consisting of the following:

• The error that prevented users from launching the Expere Config Tool utility has been resolved; users can now use this tool to update values within the configuration files above.
• The Max Cached Object field has been removed; with our recent upgrade to ehCache 2.10, users no longer need to specify how much cache needs to be allocated for a specific number of objects.

Users can access the updated Expere Config Tool utility here.

Expere Engine: Black Duck security enhancement

• Reference: PBI 370551
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

The Expere Engine is now scanned with the Black Duck Security for every external release.

StoreNode attribute enhanced

• Reference: PBI 372033
• Compliance Impacts: This defect correction is a compliance or regulatory issue.
• Documentation: Content Stylesheet

Previously, the StoreNodeAddition element could sum other elements, but not other StoreNodeAddition elements.

The Expere Engine stylesheets (AddTotalResultAttribute.xsl and GetTotalResultStoreNodeAddition.xsl) have been enhanced to include the StoreNodeAddition element so it could be included in the sum of another StoreNode element; the TotalClosingCosts StoreNodeAddition element now includes StoreNodeName=”TotalClosingCosts” and totalResult=”” attributes available in the Requirements Editor.

This behavior was necessary to subtract Total Closing Costs from another total.

New Total First, then Round Method

• Type: Enhancement
• Reference: PBI 351029
• Compliance Impacts: A New Total First, then Round Method is being added to support a future compliance-related content change (targeted for the 2016.2.2 May Content Release).
• Documentation: No document impacts

Technical Notes: The Expere Engine has been enhanced to add new elements and attributes to support the new rounding method. The new element and method will allow for the ability to total the items first, and then round the sum of them. The Expere Engine Stylesheet has been modified to add logic to utilize new elements/attributes and implement the new rounding method to calculate aggregated totals that then need to be rounded.

This content change will not be backwards-compatible with prior versions of the Expere Engine/Tools. You are encouraged to install this Engine release as soon as possible so it is in place prior to receving the content update targeted for the May content release.

Rounding Enhancement

• Type: Enhancement
• Reference: PBI 351029
• Compliance Impacts: This enhancement is a compliance or regulatory issue.
• Documentation: No document impact.

The Expere engine uses the round "To Even" method (a/k/a the bankers rounding rule). The effect of this method was that 50 cents, being the midpoint, would round to the nearest even whole number (e.g., 0, 2 ,4, ...). If an actual amount was $3.50, the rounded value would round up to the nearest even whole number which would be $4. In contrast, if the actual amount was $2.50, the rounded value would round down to the nearest even whole number which would be $2.

The Expere engine was enhanced with the Total First Rounding method to handle rounding in a different manner. The Expere engine utilizes the round “Away From Zero” method which will consistently round up at the mid-point. No content change is needed to utilized this enhancement. The enhancement is included with the Expere 2016.1.0 engine release

First page only barcode feature added

• Type: New Feature
• Reference: PBI 292273 / 364317PBI 364319PBI 364255
• Compliance Impacts: This new feature is not a compliance or regulatory issue.
• Documentation: Using First Page Only BarcodesSelect Generate and Deliver, Select And Generate, GenerateSelect And Generate and GenerateUsing First Page Only Barcodes.

Summary: Users can now apply a barcode to the first or only page of a document. For detailed information on using this feature within the Expere Document Services Tool SuiteDocument Generation Services Tool Suite, see the Select Generate and DeliverSelect And Generate, and Generate webhelp sections within the SERVICE Page Using First Page Only Barcodes webhelp pageSelect And Generate and Generate webhelp sections within the SERVICE PageUsing First Page Only Barcodes webhelp page.

Enhancement to PDFs with E-signatures

• Type: Enhancement
• Reference: PBI 374576
• Compliance Impacts: This change is a compliance or regulatory issue.
• Documentation: No document impact.

An issue had been identified with certain PDF viewers and e-signatures. Specifically, documents with e-signatures turned on but not captured, would display, and sometimes print a box around the signature field.

This has been corrected; e-signature capable documents, where an e-signature has not been captured, will no longer display or print a box around the signature field.

Expere Engine updated to latest version of Apache Commons-Collections

• Type: Enhancement
• Reference: PBI 372328
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Summary: The Apache Commons-Collections used with the Expere Engine has been upgraded to version 4.1. For detailed information on JDK classes, consult the Commons-Collections User Guide.

Expere OPPSA package behavior enhanced

• Reference: PBI 195492
• Compliance Impacts: This defect is not a compliance or regulatory issue.
• Documentation: No document impact.

Previously, when a document was removed from base content, OPPSA stopped printing when it encountered the missing document. In some instances, the system stopped printing any remaining documents depending on where the document was located.

This behavior has been enhanced; when an OPPSA package includes a document that has been removed, an error appears stating which document must be removed from the specified package in the OPPSA product.

Expere supported to use to Oracle 12

• Type: Enhancement
• Reference: PBI 365378
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: Windows Environment Software Requirements, Java Environment Software Requirements.

Summary: Expere has been validated for use with Oracle 12; for more information, and for a comprehensive list of supported requirements, see Windows Environment Software Requirements and Java Environment Software Requirements.

Special Character handling enhanced

• Reference: PBI 368230
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Issue: There are certain special characters which are ANSI printable but fail to print due to constraints in Expere code. Errors occurred in Expere when attempting to resolve special characters in the following scenarios:

• When encountering a special character with a converted integer value greater than 255.
• If a special character existed as a valid ANSI number but after being encoded to UTF-8, the Unicode value resided outside of the ANSI range.

Summary: The following enhancements have been implemented: Expere now handles special characters for static documents without resulting in any fatal errors.

• Expere now handles special characters for static documents without resulting in any fatal errors.
• Compatible characters are printed when applicable.
• Any other special characters are replaced with question marks or spaces.

Expere upgraded to Java 8 and Saxon

• Reference: PBI 302204
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: Windows Environment Software Requirements, Java Environment Software Requirements, Expere Authoring Tools.

Summary: Embedded versions of Expere .NET and Requirements Editor now utilize Java 8 and Saxon.

For more information, see the following Expere System Requirements Sections:

• Windows Environment Software Requirements
• Java Environment Software Requirements
• Expere Authoring Tools

Java and .NET Implementation Guide consolidated

• Type: Enhancement
• Reference: PBI 372968
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: Expere Implementation Guide

We have recently consolidated the .NET and Java installation procedures to now reside in one webhelp implementation, available here: Expere Implementation Guide.

TRID Rounding issue resolved

• Reference: PBI 358699
• Compliance Impacts: This defect is a compliance or regulatory issue.
• Documentation: No document impact.

Solution: These issues have been resolved; the section total now appears correctly when negative line items (fees) exist. Additionally, the "Additional Charges" and "See Addendum for add’l charges you can shop for." line items appear correctly.

GetServiceInfo API enhanced

• Reference: PBI 339775
• Compliance Impacts: This defect is not a compliance or regulatory issue
• Documentation: No document impact.

Issue: Previously, the GetServiceInfo.xml autotester test returned version number 4.1.5 for every third party library. This issue occurred as a result of our work on PBI 333176 (CRM: GetServiceInfo is not working).

Solution: We have resolved this issue; the correct version number now appears for each third party library.

Expere logging enhancements

• Type: Enhancement
• Reference: PBI 360148
• Compliance Impacts: This enhancement is not a compliance or regulatory issue.
• Documentation: No document impact.

Summary: The ExpereService.log file has been enhanced to include the Request ID from the SOAP message. If no Request IDis contained in the SOAP message, the string “null” is logged.

Expere Engine: Caching enhanced in ehcache

• Type: Enhancement
• Reference: PBI 353140 / 358632 / 350323
• Compliance Impacts: These enhancements are not a compliance or regulatory issue.
• Documentation: Expere Implementation Guides: Caching notes.

Summary: Expere has upgraded to Ehcache 2.10.0 to utilize enhanced caching capability; the following enhancements have been implemented for ehcache.xml:

• Enhancement #1: Previously there was only one level of cache on objects. Changes have been made to include two cache levels and to add images to the updated cache configuration.
• Enhancement #2: Cache memory allocation has changed in ehcache.xml. Previously, users could change the maxElementsInMemory value in the global cache (ExpereCache) or any of its smaller caches.

Now, users can adjust the maxBytesLocalHeap and maxBytesLocaldisk values in ExpereCache and its smaller caches. maxBytesLocalHeap is the percentage of allocated Java Virtual Machine (JVM) heap size while maxBytesLocalDisk allocates a specified amount of memory of the local disk for overflow caching.

For detailed information on how to change the memory allocations in the configuration file, see the Expere Implementation Guide: Caching notes.

This feature requires an Expere Engine update.

Barcode spacing issue resolved

• Type: Defect correction
• Reference: PBI 355603
• Compliance Impacts: This defect is not a compliance or regulatory issue.
• Documentation: No document impact.

Issue: Previously, the Expere Engine reserved space for ancillary barcodes on dynamic documents even though the barcode element was not included in the .REQ file.

Solution: This issue has been resolved; when generating a dynamic document and selecting an ancillary barcode option, the document will no longer reserve space for the barcode if the .REQ file does not contain a barcode element.

This feature requires an Expere Engine update.

Missing SaveInResponse element resolved

• Type: Defect Correction
• Reference: PBI 368079
• Compliance Impacts: This defect is not a compliance or regulator issue.
• Documentation: No document impact.

Issue: Previously, the SaveInResponse element was missing from the SelectResponse.xsd file but was still being returned in the response. This issue impacted the Select API.

Solution: This issue has been resolved; the SaveInDatabase element is now an optional element in the SelectResponse.xsd file.

Expere Engine: Smart quotes special characters in transaction issue resolved

• Type: Defect correction
• Reference: PBI 257585
• Compliance Impacts: This defect is not a compliance or regulatory issue.
• Documentation: No document impact.

Summary: It was reported that special characters 0145, 0146, 0147, and 0148 resulted in errors on static documents. See the Expere log example below for more information.

Solution: Quotation marks are now converted appropriately (from smart quotes to regular quotes); as a result, static and dynamic documents do not produce an error when generating a .PDF document if smart quotes are present.

This feature requires an Expere Engine update.